ci: publish releases from pre-built CI artifacts - #5626
Open
deadprogram wants to merge 1 commit into
Open
Conversation
deadprogram
changed the title
deadprogram
changed the title
deadprogram
changed the title
|
Size difference with the dev branch: Binary size differenceflash ram before after diff before after diff 19684 19684 0 0.00% 7052 7052 0 0.00% tinygo build -size short -o ./build/test.hex -target=feather-rp2040 ./examples/adafruit4650 63228 63228 0 0.00% 6788 6788 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/adt7410/main.go 10024 10024 0 0.00% 5348 5348 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/adxl345/main.go 14628 14628 0 0.00% 7396 7396 0 0.00% tinygo build -size short -o ./build/test.hex -target=pybadge ./examples/amg88xx 10184 10184 0 0.00% 5348 5348 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/apa102/main.go 12592 12592 0 0.00% 7172 7172 0 0.00% tinygo build -size short -o ./build/test.hex -target=nano-33-ble ./examples/apds9960/proximity/main.go 11136 11136 0 0.00% 5360 5360 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/apa102/itsybitsy-m0/main.go 7588 7588 0 0.00% 2312 2312 0 0.00% tinygo build -size short -o ./build/test.hex -target=microbit ./examples/at24cx/main.go 9272 9272 0 0.00% 5340 5340 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/bh1750/main.go 8660 8660 0 0.00% 5340 5340 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/blinkm/main.go 71408 71408 0 0.00% 3656 3656 0 0.00% tinygo build -size short -o ./build/test.hex -target=pinetime ./examples/bma42x/main.go 67120 67120 0 0.00% 6804 6804 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/bmi160/main.go 28952 28952 0 0.00% 5380 5380 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/bmp180/main.go 65720 65720 0 0.00% 6828 6828 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/bmp280/main.go 13080 13080 0 0.00% 5412 5412 0 0.00% tinygo build -size short -o ./build/test.hex -target=trinket-m0 ./examples/bmp388/main.go 24024 24024 0 0.00% 6220 6220 0 0.00% tinygo build -size short -o ./build/test.hex -target=metro-rp2350 ./examples/bno08x/i2c/main.go 8008 8008 0 0.00% 3344 3344 0 0.00% tinygo build -size short -o ./build/test.hex -target=bluepill ./examples/ds1307/sram/main.go 22116 22116 0 0.00% 3548 3548 0 0.00% tinygo build -size short -o ./build/test.hex -target=bluepill ./examples/ds1307/time/main.go 30556 30556 0 0.00% 5576 5576 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/ds3231/alarms/main.go 44492 44492 0 0.00% 5576 5576 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/ds3231/basic/main.go 4592 4592 0 0.00% 2272 2272 0 0.00% tinygo build -size short -o ./build/test.hex -target=microbit ./examples/easystepper/main.go 71884 71884 0 0.00% 7588 7588 0 0.00% tinygo build -size short -o ./build/test.hex -target=itsybitsy-m0 ./examples/flash/console/spi 67996 67996 0 0.00% 9628 9628 0 0.00% tinygo build -size short -o ./build/test.hex -target=pyportal ./examples/flash/console/qspi 7128 7128 0 0.00% 2276 2276 0 0.00% tinygo build -size short -o ./build/test.hex -target=microbit ./examples/gc9a01/main.go 694072 694072 0 0.00% 131564 131564 0 0.00% |
The Linux, macOS and Windows workflows build every file that a release needs when the release branch is pushed. The new Release workflow finds those runs for the tagged commit, waits for them, and collects their nine files into a draft release. It builds nothing, so what ships is what was tested. The release notes come from the CHANGELOG.md entry for that version. Signed-off-by: Ron Evans <ron@hybridgroup.com>
Member
Author
|
Currently testing this in a fork... |
deadprogram
force-pushed
the
ci-release-workflow
branch
from
August 29, 2026 10:10
38435f5 to
b3f4262
Compare
Member
Author
|
Tested end to end on a fork, https://github.com/deadprogram/tinygo. The first attempt found a real bug. The workflow now uses With that fix, a stub run that produces the nine correctly named files passed
Negative cases:
The run with the real builds is in progress. I will report the result. |
Member
Author
|
The run with the real builds passed. Fork run: https://github.com/deadprogram/tinygo/actions/runs/33247041566 The Linux, macOS and Windows workflows all concluded Every published asset digest equals the digest of the artifact its build job The |
Member
Author
|
Once #5627 is merged we can merge this one! |
Member
Author
|
#5627 has been merged so this is now ready! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is to improve the release process.
CI already builds every file that a release needs. Only the publication is
manual: download nine artifacts from three runs, create the release, attach the
files, paste the CHANGELOG entry.
This adds a
Releaseworkflow that does that work. It builds nothing. TheLinux, macOS and Windows workflows already run on the
releasebranch push, sothe workflow finds those runs for the tagged commit, waits for them, and
collects their artifacts. What ships is what was tested, and no existing
workflow changes.
Trigger. A
v*tag push starts it.workflow_dispatchwith a tag inputallows a second attempt without a move of the tag.
Checks.
vplus the version ingoenv/version.go, because the filenames come from that constant. A
-devversion stops the release.never built stops the release.
half complete release.
Files are found by file name, not by artifact name. The artifact names are
not uniform.
linux.ymluploads the amd64 tarball and .deb under their filenames, but the arm and arm64 jobs put two files under one
linux-<goarch>-double-zipped-<version>name, andbuild-macos.ymldoes thesame. A search by file name handles both, and a later cleanup of those names
cannot break this workflow.
Release notes come from the CHANGELOG.md entry for that version, through the
new
.github/workflows/extract-changelog.sh. The release is a draft, so thenotes can be reviewed before publication. The title is the bare version, which
matches every release from 0.27.0 to 0.41.1.
No checksum file. GitHub keeps a SHA-256 digest of every asset. BUILDING.md
gives the command that prints them.
BUILDING.md gets a "Publish a release" section with the full procedure.
Tested
Local:
sh -non the script,bash -non everyrunblock, and a YAML parse.extract-changelog.shagainst the newest entry, a middle entry, the oldestentry (the end of file case) and an unknown version.
names, for the complete case and for a missing file.
-dev, wrong tag and correct tag cases.Still to do, because it cannot run locally: an end to end run on a fork, and the
two negative cases.
Follow-up
linux.yml:465,linux.yml:471andbuild-macos.yml:106still use the*-double-zipped-*names. Nodownload-artifactstep reads them, so a renameis safe, but it belongs in its own PR.